Call Transformations

The Call Transformation feature allows Boomi Cloud API Management endpoints with the ability to plug in pre-processors and post-processors (Boomi Cloud API Management Connectors).

The Traffic Manager can apply processing logic to an API request before it is sent to the host API servers and after the response is returned from the client API servers. A typical use case for processing logic is protocol translation.

For example, when a developer makes an XML-RPC to the client API servers that require the API requests to be REST-based, the Traffic Manager translates this request to a REST-based request using specific translation logic. Protocol translation can make the API appear more robust by supporting multiple protocols when, in fact, it only supports a single protocol. Other common use-cases for the processing adapter include content injection, content filtering, and content transformation.

note

• The Call Transformations tab will be enabled only when the Boomi-controlled back office Config Feature flag Enable External Call Transformation is enabled for your area in Boomi Cloud API Management. Once this feature is enabled, it cannot be turned off.

• ASR (Application Service Registry) services set up in Boomi Cloud will only be available in ASR Picker if they are marked Private. The Services defined for Post methods with no variable set on the path can only be successfully selected on the Call Transformation page. This means that query parameters can't be added, and none of the path values for the endpoint can be dynamically populated during run-time.

The Call Transformations page for an endpoint includes the following fields:

Processing Adapter

This field is used to specify class file of custom logic that the Traffic Manager uses to perform pre-processing or post-processing of an API call.

Perform Pre-processing

This field configures the Traffic Manager to process the API request before it is sent to the client API server. When enabled, the Traffic Manager applies custom processing logic to an API call before the request is sent to the client API servers.

Data to make available for pre-processing

This field configures the Traffic Manager to add new values or modify the existing values within the incoming API call before passing it to the client API servers.

Perform Post-processing

This field configures the Traffic Manager to process the API call before it is sent to the client API server. When enabled, the Traffic Manager applies custom processing logic to the response received from the client API servers.

Data to make available for post-processing

This field configures the Traffic Manager to add new values or modify the existing values within the incoming API call before passing it to the client API servers.

Next Steps

Configure call transformations for an endpoint. To learn more, refer to Configuring Call Transformation for an Endpoint .